-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_Uglify the current member of move_iterator #1080
Conversation
8cac1dd
to
9ebcb32
Compare
For final review, we should think about the bincompat consequences. (I think they're acceptable, as mentioned above.) |
I don't recall CLR metadata knowing about access control at all, or caring about the names of members: it's primarily concerned with the sizes of non-static data members and their offsets within the complete object's layout. (We even had success with the |
Thank you for making our code, and our lives, a little |
Looking at
counted_iterator
I found thatmove_iterator
has a non-ugly membercurrent
.The same forreverse_iterator
As this is a purely private member it is not user accessible and should be
_Ugly